Image processing apparatus, information processing method, and storage medium

ABSTRACT

An image processing apparatus includes a reception unit configured to receive a session start message, a determination unit configured to determine whether the session start message received by the reception unit is a session start message from a public Internet Protocol network or a session start message from a local Internet Protocol network, an acquisition unit configured to acquire a media type included in the session start message received by the reception unit, and a control unit configured to determine whether a start of a session is allowed, based on a result determined by the determination unit and the media type acquired by the acquisition unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation, and claims the benefit, of U.S.patent application Ser. No. 14/222,450, presently pending and filed onMar. 21, 2014, and claims the benefit of, and priority to, JapanesePatent Application No. 2013-067075 filed Mar. 27, 2013, whichapplications are hereby incorporated by reference herein in theirentireties.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to an image processing apparatus, aninformation processing method, and a storage medium.

Description of the Related Art

Recently, attention has been paid to an Internet Protocol facsimile(IPFAX) that transmits and receives a facsimile (FAX) via an InternetProtocol (IP) network.

The Session Initiation Protocol (SIP) is used for a call connectionbetween IPFAX devices, and the T.38 protocol for data communication. AnIPFAX using the T.38 protocol, which can perform communication fasterthan a conventional analog FAX, can transmit and receive an image in ashorter time.

The IPFAX performs FAX communication between devices connected to anintranet (local IP network) or FAX communication between devicesconnected to a public IP network.

Communication within an intranet, which uses a company network or alocal network for communication, does not involve communication fees.

On the other hand, communication on a public IP network, likecommunication on an existing analog public network, employs a pay-persystem that involves a fee for each FAX communication.

Conventional IPFAX devices cannot be connected to the two types of IPnetwork, i.e., local and public IP networks, at the same time.Therefore, conventional IPFAX can operate in any one of the two modes(local IP network mode and public IP network mode) selected according toa setting made by a user, or can operate only in one of the two modes.

In recent years, as a network has become diversified, there has been aneed for an IPFAX device that can communicate with any of a device on alocal IP network and a device on a public IP network without requiring auser to change the user setting.

According to the SIP protocol for call connections, an INVITE message isused to request a connection. An INVITE message includes a descriptiondescribed in Session Description Protocol (SDP) (See Japanese PatentApplication Laid-Open No. 2012-90213).

The SDP is a protocol used to describe a multimedia session. Forexample, the SDP is used to describe information about the type of mediato be communicated, that is, whether an audio is to be communicated(audio), whether an image is to be communicated (image, application),and whether a video is to be communicated (video). The media type (m) isused to determine what is to be communicated. Normally, “m=audio” isspecified for IP telephony, and “m=image” or “m=application” isspecified for IPFAX via a public IP network.

Because T.38 IPFAX usually does not provide the phone function, it isdesirable to reject an INVITE message received from a phone. Inparticular, on a public IP network, a caller is charged for a call inspite of the fact that communication cannot be performed. To addressthis problem, in a conventional method, the media type “m=audio” isrejected but the media type “m=image” or “m=application” is accepted.

However, when IPFAX communication is performed via a local IP network, amessage is transmitted usually via an SIP server that has a routingfunction and a registration function. This sometimes requires the userto follow a specific procedure depending on the type of the SIP server.

For example, the SIP server provided by a company requires a procedurein which “audio” is specified for the SDP media type of a first INVITEmessage, and after that, the media type is changed to “image”.Therefore, if all INVITE messages are simply rejected because the mediatype is “audio”, there is an issue that IPFAX communication cannot beperformed via a local IP network.

There is a T.38 gateway (T.38 GW) capable of connecting an analog FAX toan IP network as an IPFAX. However, the T.38 GW provided by a companytransmits an INVITE message in which “audio” is specified for the mediatype as described above. Normally, the T.38 GW is connected to a localIP network.

SUMMARY OF THE INVENTION

The present invention is directed to an image processing apparatusallowing connection from both a device on a local IP network and adevice on a public IP network, and preventing unnecessary charging.

An image processing apparatus includes a reception unit configured toreceive a session start message, a determination unit configured todetermine whether the session start message received by the receptionunit is a session start message from a public Internet Protocol networkor a session start message from a local Internet Protocol network, anacquisition unit configured to acquire a media type included in thesession start message received by the reception unit, and a control unitconfigured to determine whether a start of a session is allowed, basedon a result determined by the determination unit and the media typeacquired by the acquisition unit.

Further features of the present invention will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a system configuration ofa FAX system that includes IPFAX devices.

FIG. 2 is a diagram illustrating an example of a hardware configurationof an IPFAX 1.

FIG. 3 is a diagram illustrating an example of a structure of an INVITEmessage and an SDP description.

FIG. 4 is a diagram illustrating an example of an address setting screenof a gateway and an SIP server used by the IPFAX 1.

FIG. 5 is a diagram illustrating an example of a communication sequencewhen an image is transmitted from an IPFAX 2 to the IPFAX 1.

FIG. 6 is a diagram illustrating an example of a communication sequencewhen an image is transmitted from an IPFAX 3 to the IPFAX 1.

FIG. 7 is a diagram illustrating an example of a communication sequencewhen a call is transmitted from an IP phone to the IPFAX 1.

FIG. 8 is a flowchart illustrating an example of information processingperformed when the IPFAX 1 receives an incoming call from the IPFAX 2,the IPFAX 3, or the IP phone.

DESCRIPTION OF THE EMBODIMENTS

Various exemplary embodiments, features, and aspects of the inventionwill be described in detail below with reference to the drawings.

FIG. 1 is a diagram illustrating an example of a system configuration ofa FAX system that includes IPFAX devices. For the sake of simplicity, anIPFAX device is simply described as an IPFAX, and a FAX device is simplydescribed as a FAX. An IPFAX is an example of an image processingapparatus.

The FAX system includes a local IP network 1000 and a public IP network1003.

Home gateways (HGW) 1002 and 1010 are gateways for connecting to thepublic IP network 1003.

An IPFAX 1 (1001) is an IPFAX connected to the local IP network 1000.The IPFAX 1 (1001) can communicate also with the public IP network 1003via the HGW 1002.

An IPFAX 2 (1004) is an IPFAX connected to the public IP network 1003.An IP phone 1009 and the IPFAX2 (1004) are connected to the public IPnetwork 1003 via the HGW 1010. An SIP server 1005 is connected to thelocal IP network 1000. An IPFAX 3 (1006) is an IPFAX connected to thelocal IP network 1000. The IPFAX 3 (1006) can communicate with the IPFAX1 (1001) via the SIP server 1005.

A T.38 gateway (T.38 GW) 1007 is a gateway (GW) connected to a publicswitched telephone network (PSTN) network 1011 and the local IP network1000. An analog FAX 1008 is an analog FAX connected to the PSTN network1011. The T.38 GW 1007 converts an SIP call connection to an analogphone call connection, and the T.38 protocol to the T.30 protocol, inreal time to enable intercommunication between an IPFAX and an analogFAX.

An IPFAX has an IPFAX function of sending and receiving a FAX via an IPnetwork.

FIG. 2 is a diagram illustrating an example of a hardware configurationof the IPFAX 1.

A central processing unit (CPU) 801 controls the devices in the IPFAX 1(1001) and executes the processing of the flowchart, which will bedescribed below, based on a control program stored in a read only memory(ROM) 808.

A display/operation unit 803 displays a screen related to settingsdescribed below, and receives information entered via an operation.

A scanner unit 804 reads a document.

A print unit 805 prints print data saved in a random access memory (RAM)809 or a hard disk drive (HDD) 810.

The ROM 808 stores various control programs and data. The RAM 809includes a work area for the CPU 801, a save area in which data is savedduring error processing, and a load area in which a control program isloaded.

The HDD 810 saves therein various control programs and print data suchas set IP addresses, which will be described below.

A network interface (I/F) unit 813 is connected to the public IP network1003 via the local IP network 1000 and the HGW 1002.

A T.38 protocol creation/analysis unit 814 has the function ofgenerating facsimile transmission information based on the InternationalTelecommunication Union Telecommunication Standardization Sector (ITU-T)Recommendation T.38 protocol, and the function of extracting facsimiletransmission information from a received protocol.

An IP packet creation/analysis unit 806 maps the ITU-T RecommendationT.38 protocol to an IP packet, and has the function of extracting theITU-T Recommendation T.38 protocol from a received IP packet.

An image conversion control unit 807 performs compression/decompression,zooming, and linear density conversion of an image to be transmitted andreceived using FAX communication. The CPU 801 executes processing basedon the programs stored in the ROM 808 or the HDD 810 to implement asoftware function of the IPFAX 1 and the processing according to aflowchart described below.

The T.38 protocol creation/analysis unit 814 and the IP packetcreation/analysis unit 806 may be installed on the IPFAX 1 as software.This software is implemented when the CPU 801 executes the processingbased on the programs.

FIG. 3 is a diagram illustrating an example of a structure of an INVITEmessage and an SDP description.

The INVITE message includes an SIP start line 2001, an SIP header field2002, a blank line 2003, and an SIP message body 2004 described in theSDP. The SDP description may sometimes be the one such as an SIP messagebody 2005. Because the details of each field and each line is describedin recommendation reports such as the Request for Comments (RFC) 4566,their description is omitted here. The following describes only themedia type described in the SDP description. Information about the typeof media to be communicated is described in a line beginning with “m=”in the SIP message body 2004 or 2005. For example, the SDP description“m=audio” in the SIP message body 2004 indicates that the media type isan audio (voice). Similarly, the SIP message body 2005 includes the SDPdescription “m=image” indicating that the media type is an image.

The INVITE message is an example of a session start message.

FIG. 4 is a diagram illustrating an example of an IP address settingscreen of a gateway and an SIP server used by the IPFAX 1 (1001). Asetting screen 3001 includes an HGW IP address registration field 3002,a local SIP server IP address registration field 3003, and T.38 GW IPaddress registration fields 3004, 3005, and 3006. The HGW IP addressregistration field 3002 contains the IP address of an HGW that is agateway used to connect an IPFAX to a public IP network. The local SIPserver IP address registration field 3003 contains the IP address of alocal SIP server used to connect an IPFAX to a local IP network. Each ofthe T.38 GW IP address registration fields 3004, 3005, and 3006 containsthe IP address of a T.38 GW used to perform communication between anIPFAX and an analog FAX. In this example, up to three T.38 GWs may beregistered. However, the number of T.38 GWs used in this example doesnot limit the present exemplary embodiment.

As illustrated in FIG. 4, the IP address of an SIP server on a local IPnetwork, the IP address of an HGW used to connect to a public IPnetwork, and the IP address of a T.38 GW may be registered in an IPFAX.

A home gateway, a local SIP server, and a T.38GW are examples ofdevices.

FIG. 5 is a diagram illustrating an example of a communication sequencewhen an image is transmitted from the IPFAX 2 (1004) to the IPFAX 1(1001). In practice, a signal is transmitted between the HGW 1010 andthe HGW 1002 via various servers and gateways on the public IP network1003. The description of those servers and gateways is omitted here forsimplicity.

In step S4001, the IPFAX 2 (1004) transmits an INVITE message to the HGW1010 to make a session connection (session start) request.

In step S4002, the HGW 1010 transmits the INVITE message to the HGW1002.

In step S4003, the HGW 1002 transmits the INVITE message to the IPFAX 1(1001). Because the INVITE message in steps S4001, S4002, and S4003 istransmitted using an IPFAX communication over the public IP network, themedia type is “image” or “application”.

As will be described below in FIG. 8, the IPFAX 1 (1001) analyzes the IPpacket of the INVITE message transmitted from the HGW 1002, acquires theIP address, and compares the acquired IP address with the IP addressesregistered via the screen illustrated in FIG. 4. Because the IP addressof the home gateway set in the field 3002 matches the IP addressincluded in the INVITE message, the IPFAX 1 (1001) determines that theINVITE message received in step S4003 is transmitted from the HGW 1002.Therefore, the IPFAX 1 (1001) determines that the transmission source ofthis INVITE message is a device connected to the public IP network.

In step S4004, the IPFAX 1 (1001) transmits to the HGW 1002 a successmessage (200 OK) including a status code of 200 indicating that theincoming call is acceptable.

In step S4005, the HGW 1002 transmits “200 OK” to the HGW 1010.

In step S4006, the HGW 1010 transmits “200 OK” to the IPFAX 2 (1004).

After that, in step S4007, an IPFAX image is transmitted from the IPFAX2 (1004) to the IPFAX 1 (1001) via the HGWs 1010 and 1002 using imagecommunication based on the T.38 protocol.

The session is then disconnected by disconnection processing in stepsS4008, S4009, S4010, S4011, S4012, and S4013.

FIG. 6 is a diagram illustrating an example of a communication sequencewhen an image is transmitted from the IPFAX 3 (1006) to the IPFAX 1(1001). On the SIP server 1005, the procedure is assumed to be necessaryin which a session is once established by specifying “audio” for themedia type, and after that, reconnected by specifying “image” for themedia type.

In step S5001, the IPFAX 3 (1006) transmits an INVITE message to the SIPserver 1005 to make a session connection request.

In step S5002, the SIP server 1005 transmits the INVITE message to theIPFAX 1 (1001). In the INVITE message in steps S5001 and S5002, “audio”is specified for the media type.

The IPFAX 1 (1001) analyzes the IP packet of the INVITE messagetransmitted from the SIP server 1005, acquires the IP address, andcompares the acquired IP address with the IP addresses registered viathe screen illustrated in FIG. 4. The IP address of the local SIP serverset in the field 3003 matches the IP address included in the INVITEmessage. Therefore, the IPFAX 1 (1001) determines that the INVITEmessage received in step S5002 is transmitted from the local SIP server1005. As a result, the IPFAX 1 (1001) determines that the transmissionsource of this INVITE message is a device connected to the local IPnetwork.

In step S5003, the IPFAX 1 (1001) transmits, to the SIP server 1005,“200 OK” indicating that the incoming call is acceptable.

In step S5004, the SIP server 1005 transmits “200 OK” to the IPFAX 3(1006).

After that, in step S5005, IPFAX 1 (1001) transmits to the SIP server1005 an INVITE message in which the media type “image” is specified,according to the specific procedure described above.

In step S5006, the SIP server 1005 transmits to the IPFAX 3 (1006) theINVITE message in which the media type “image” is specified.

In steps S5007 and S5008, “200 OK” is transmitted from the IPFAX 3(1006) to the IPFAX 1 (1001), and a session is established with themedia type “image”. In step S5009, an IPFAX image is transmitted fromthe IPFAX 3 (1006) to the IPFAX 1 (1001) via the SIP server 1005 usingan image communication based on the T.38 protocol.

The session is then disconnected by disconnection processing in stepsS5010, S5011, S5012, and S5013.

FIG. 7 is a diagram illustrating an example of a communication sequencewhen a call is transmitted from the IP phone 1009 to the IPFAX 1 (1001).

In practice, a signal is transmitted between the HGW 1010 and the HGW1002 via various servers and gateways on the public IP network 1003. Thedescription of those servers and gateways is omitted here forsimplicity.

In step S6001, the IP phone 1009 transmits an INVITE message to the HGW1010 to make a session connection request.

In step S6002, the HGW 1010 transmits the INVITE message to the HGW1002.

In step S6003, the HGW 1002 transmits the INVITE message to the IPFAX 1(1001).

Because the INVITE message in steps S6001, S6002, and S6003 is a callfrom the IP phone, the media type is “audio”.

If the IPFAX 1 (1001) receives the call at this point, the usage fee ofthe public IP network is charged in spite of the fact that the call withthe IP phone cannot be made.

The IPFAX 1 (1001) in the present exemplary embodiment analyzes the IPpacket of the INVITE message transmitted from the HGW 1002, acquires theIP address, and compares the acquired IP address with the IP addressesregistered via the screen illustrated in FIG. 4. Because the IP addressof the home gateway set in the field 3002 matches the IP addressincluded in the INVITE message, the IPFAX 1 (1001) determines that theINVITE message received in step S6003 is transmitted from the HGW 1002.Therefore, the IPFAX 1 (1001) determines that the transmission source ofthis INVITE message is a device connected to the public IP network.

If the device connected to the public IP network is an IPFAX, an INVITEmessage in which “image” or “application” is specified for the mediatype should be transmitted. Therefore, the IPFAX 1 (1001) determinesthat the device on the public IP network, which has transmitted theINVITE message in which the media type “audio” is specified, is not anIPFAX.

Therefore, in step S6004, the IPFAX 1 (1001) transmits to the HGW 1002 amedia mismatch error (status code 488, warning code 304) (a response488-304) indicating the rejection of the incoming call.

In step S6005, the HGW 1002 transmits the response 488-304 to the HGW1010.

In step S6006, the HGW 1010 transmits the response 488-304 to the IPphone 1009. In this communication, a session is not established.

FIG. 8 is a flowchart illustrating an example of information processingperformed when the IPFAX 1 (1001) receives an incoming call from theIPFAX 2 (1004), IPFAX 3 (1006), or IP phone 1009. The IPFAX 2 (1004) isconnected to the public IP network 1003, the IPFAX 3 (1006) is connectedto the local IP network 1000, and the IP phone 1009 is connected to thepublic IP network 1003.

First, in step S7001, the IPFAX 1 (1001) receives an INVITE message.

In step S7002, the IPFAX 1 (1001) acquires the transmission source IPaddress from the IP packet of the INVITE message. The IPFAX 1 (1001)compares the acquired transmission source IP address with the IPaddresses registered via the screen illustrated in FIG. 4. If thetransmission source IP address matches the IP address of the homegateway set in the field 3002, as a result of the comparison, the IPFAX1 (1001) determines that the INVITE message is transmitted from a deviceon the public IP network. If the transmission source IP address matchesthe IP address of the SIP server set in the field 3003, as a result ofthe comparison, the IPFAX 1 (1001) determines that the INVITE message istransmitted from a device on the local IP network. The IPFAX 1 (1001)determines the transmission source of the INVITE message similarly ifthe transmission source IP address matches one of the IP addresses ofT.38 GWs set in the fields 3004, 3005, and 3006. That is, the IPFAX 1(1001) determines that the INVITE message is transmitted from an analogFAX connected to the T.38 GW connected to the local IP network. If theacquired transmission source IP address does not match any of theregistered IP addresses, it is estimated that the INVITE message isreceived not via a gateway or an SIP server, but directly from a deviceconnected in the peer-to-peer mode. In this case, the IPFAX 1 (1001)determines that the INVITE massage is transmitted from a device on thelocal IP network as well.

In step S7003, the IPFAX 1 (1001) acquires a media type from the SDPdescription included in the INVITE message.

In step S7004, if the transmission source is the local IP network asresult of the acquisition in step S7002 (“LOCAL IP NETWORK” in stepS7004), the IPFAX 1 (1001) advances the processing to step S7005. If thetransmission source is the public IP network (“PUBLIC IP NETWORK” instep S7004), the IPFAX 1 (1001) advances the processing to step S7006.

In step S7005, if the media type acquired in step S7003 is “audio”,“image”, or “application” (YES in step S7005), the IPFAX 1 (1001)advances the processing to step S7007. If the media type is none of them(for example, the media type is “video”) (NO in step S7005), the IPFAX 1(1001) advances the processing to step S7008.

In step S7006, if the media type acquired in step S7003 is “image” or“application” (YES in step S7006), the IPFAX 1 (1001) advances theprocessing to step S7007. If the media type is none of them, (forexample, the media type is “audio” or “video”) (NO in step S7006), theIPFAX 1 (1001) advances the processing to step S7008.

In step S7007, the IPFAX 1 (1001) accepts the incoming call, transmitsto the transmission source a response indicating a successfultransmission (status code 200), and then advances the processing to stepS7009.

In step S7008, the IPFAX 1 (1001) rejects the incoming call, andtransmits a media mismatch error (status code 488, warning code 304) tothe transmission source.

In step S7009, the IPFAX 1 (1001) receives an IPFAX image. Afterreceiving the image, the IPFAX 1 (1001) advances the processing stepS7010.

In step S7010, the IPFAX 1 (1001) disconnects the session.

An exemplary embodiment of the present invention is also implemented byexecuting the following processing. That is, software (a program) forimplementing the function of the exemplary embodiment described above issupplied to a system or an apparatus via a network or various storagemedia. The computer (or CPU or micro processing unit (MPU)) of thesystem or the apparatus reads the program and executes the processing.

According to the exemplary embodiments described above, on a public IPnetwork, an INVITE message is rejected if the media type “audio” isspecified in the INVITE message received from a phone with whichcommunication cannot be performed. This prevents unnecessarycommunication fee from being incurred by the caller side. In addition,on a local IP network, an INVITE message in which the media type “audio”is specified is accepted according to a specific procedure, wherebyIPFAX communication can be performed.

Therefore, according to the present invention, connection from both adevice on a local IP network and a device on a public IP network can beperformed, and at the same time, unnecessary charging can be prevented.

Embodiments of the present invention can also be realized by a computerof a system or apparatus that reads out and executes computer executableinstructions recorded on a storage medium (e.g., non-transitorycomputer-readable storage medium) to perform the functions of one ormore of the above-described embodiment(s) of the present invention, andby a method performed by the computer of the system or apparatus by, forexample, reading out and executing the computer executable instructionsfrom the storage medium to perform the functions of one or more of theabove-described embodiment(s). The computer may comprise one or more ofa central processing unit (CPU), micro processing unit (MPU), or othercircuitry, and may include a network of separate computers or separatecomputer processors. The computer executable instructions may beprovided to the computer, for example, from a network or the storagemedium. The storage medium may include, for example, one or more of ahard disk, a random-access memory (RAM), a read only memory (ROM), astorage of distributed computing systems, an optical disk (such as acompact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™),a flash memory device, a memory card, and the like.

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

What is claimed is:
 1. A communication method executed by an imageprocessing apparatus which is capable of performing an Internet Protocolfacsimile communication via an Internet Protocol network, theinformation processing method comprising: receiving an INVITE message inwhich audio is specified for the media type in an SIP (SessionInitiation Protocol) for establishing a session; determining whether thereceived INVITE message is transmitted via a SIP server; establishing asession and performing the Internet Protocol facsimile communicationusing the established session in a case where it is determined that thereceived INVITE message is transmitted via the SIP server, wherein thesession is not established and the Internet Protocol facsimilecommunication is not performed in a case where it is determined that thereceived INVITE message is transmitted not via the SIP server.
 2. Thecommunication method according to claim 1, wherein it is determined thatthe received INVITE message is transmitted not via the SIP server in acase where the received INVITE message is transmitted via a Gatewayserver.
 3. The communication method according to claim 1, wherein in acase where it is determined that the received INVITE message istransmitted via the SIP server, a message for approving theestablishment of the session is transmitted, and in a case where it isdetermined that the received INVITE message is transmitted not via theSIP server, a message for disapproving the establishment of the sessionis transmitted.
 4. The communication method according to claim 3,wherein an INVITE message in which an image or an application isspecified for the media type is transmitted after transmitting themessage for approving the establishment of the session.
 5. Thecommunication method according to claim 1, wherein it is determinedwhether the received INVITE message is transmitted via the SIP server byreferring to an IP packet of the received INVITE message.
 6. Thecommunication method according to claim 1, wherein in a case where anINVITE message in which an image or an application is specified for themedia type is received, a session is established regardless of atransmission source of the received INVITE message.
 7. The communicationmethod according to claim 1, wherein the SIP server requires a procedureincluding, after establishing a session once by communicating an INVITEmessage in which audio is specified for the media type, re-establishingthe session by communicating an INVITE message in which an image or anapplication is specified for the media type.
 8. The communication methodaccording to claim 1, wherein the Gateway is a T.38 Gateway provided bya predetermined company.
 9. The communication method according to claim1, wherein the Gateway is Home Gateway.
 10. The communication methodaccording to claim 8, wherein the T.38 Gateway requires a procedureincluding, after establishing a session once by transmitting an INVITEmessage in which audio is specified for the media type, re-establishingthe session by communicating an INVITE message in which an image or anapplication is specified for the media type.
 11. An image processingapparatus which is capable of performing an Internet Protocol facsimilecommunication via an Internet Protocol network, the informationprocessing apparatus comprising: a receiver that receives an INVITEmessage in which audio is specified for the media type in an SIP(Session Initiation Protocol) for establishing a session; a controllerthat determines whether the received INVITE message is transmitted via aSIP server, and a controller that establishes a session and performingthe Internet Protocol facsimile communication using the establishedsession in a case where it is determined that the received INVITEmessage is transmitted via the SIP server, wherein the session is notestablished and the Internet Protocol facsimile communication is notperformed in a case where it is determined that the received INVITEmessage is transmitted not via the SIP server.
 12. The image processingapparatus according to claim 11, wherein it is determined by thecontroller that the received INVITE message is transmitted not via theSIP server in a case where the received INVITE message is transmittedvia a Gateway server.
 13. The image processing apparatus according toclaim 11, wherein in a case where it is determined by the controllerthat the received INVITE message is transmitted via the SIP server, amessage for approving the establishment of the session is transmitted,and in a case where it is determined by the controller the receivedINVITE message is transmitted not via the SIP server, a message fordisapproving the establishment of the session is transmitted.
 14. Theimage processing apparatus according to claim 13, wherein an INVITEmessage in which an image or an application is specified for the mediatype is transmitted after transmitting the message for approving theestablishment of the session.
 15. The image processing apparatusaccording to claim 11, wherein it is determined whether the receivedINVITE message is transmitted via the SIP server by referring to an IPpacket of the received INVITE message.
 16. The image processingapparatus according to claim 11, wherein in a case where an INVITEmessage in which an image or an application is specified for the mediatype is received, a session is established regardless of a transmissionsource of the received INVITE message.
 17. The image processingapparatus according to claim 11, wherein the Gateway is Home Gateway.18. The image processing apparatus according to claim 11, wherein theGateway is a T.38 Gateway provided by a predetermined company.